This PR has a migration; here is the generated SQL for src/sentry/migrations/1115_projectdebugfile_add_objectstore_columns.py

for 1115_projectdebugfile_add_objectstore_columns in sentry

--
-- Alter field file on projectdebugfile
--
SET CONSTRAINTS "sentry_projectdsymfile_file_id_bdf41a41_fk_sentry_file_id" IMMEDIATE; ALTER TABLE "sentry_projectdsymfile" DROP CONSTRAINT "sentry_projectdsymfile_file_id_bdf41a41_fk_sentry_file_id";
ALTER TABLE "sentry_projectdsymfile" ALTER COLUMN "file_id" DROP NOT NULL;
ALTER TABLE "sentry_projectdsymfile" ADD CONSTRAINT "sentry_projectdsymfile_file_id_bdf41a41_fk_sentry_file_id" FOREIGN KEY ("file_id") REFERENCES "sentry_file" ("id") DEFERRABLE INITIALLY DEFERRED NOT VALID;
ALTER TABLE "sentry_projectdsymfile" VALIDATE CONSTRAINT "sentry_projectdsymfile_file_id_bdf41a41_fk_sentry_file_id";
--
-- Add field storage_path to projectdebugfile
--
ALTER TABLE "sentry_projectdsymfile" ADD COLUMN "storage_path" text NULL;
--
-- Add field content_type to projectdebugfile
--
ALTER TABLE "sentry_projectdsymfile" ADD COLUMN "content_type" text NULL;
--
-- Add field file_size to projectdebugfile
--
ALTER TABLE "sentry_projectdsymfile" ADD COLUMN "file_size" bigint NULL;
--
-- Add field date_created to projectdebugfile
--
ALTER TABLE "sentry_projectdsymfile" ADD COLUMN "date_created" timestamp with time zone NULL;

Is the idea behind making the file field nullable in the model and adding assertions that this way we save ourselves a migration? In principle, it would work just as well to only add the new columns and do the nullability separately, right?

Yeah @loewenheim, we could very well split this into 2 separate migrations, would it be preferable to do it that way?
It's my first time creating a migration, so I don't really know what factors should be considered.

The intention was not really to spare a migration, but to make the File nullable while at the same time introducing the alternative, as if this were an enum you add a variant to.
A ProjectDebugFile with a NULL File doesn't make too much sense to me, unless an alternative way to point to a file exists.

If having two separate migrations isn't a concern, I would prefer it if the file field was made nullable at the point where it's actually possible for a debug file to have null there.

Yeah that makes sense, I'll change it.

I'm going to merge this as is, as making the File column nullable when it can actually be null would add more changes to #117502 where we add the write capability, which is already a large change.

FS-364